home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
bbs
/
elvis15.zip
/
ERROR.QB
< prev
next >
Wrap
Text File
|
1996-11-08
|
5KB
|
117 lines
QuickBasic Error codes
DoorFrame uses the QB error codes.
---------------------------------------------------------------------------
2 Syntax error 61 Disk full
5 Illegal function call 62 Input past end of file
6 Overflow 63 Bad record number
7 Out of memory 64 Bad file name
11 Division by zero 67 Too many files
13 Type mismatch 68 Device Unavailable
24 Device timeout 69 Comm-buffer overflow
25 Device fault 70 Permission denied
52 Bad file name or number 71 Disk not ready
53 File not found 72 Disk media error
55 File already open 74 Rename across disk
57 Device I/O error 75 Path/File access error
58 File already exists 76 Path not found
59 Bad record length
Here's a listing of SOME of the most common errors that have been
occurring...Mostly due to NOT reading the DOC's carefully...
**** ERROR #52 - Bad file name or number
ERROR #64 - Bad file name
CAUSE: Lines 8 & 9 in the .CFG file are not setup correctly.
CURE: These lines are specifying the path, type, name of the bulletins
if any that you wish the door to create.
* Wildcat! Users (any version)
If you are running a Wildcat! BBS (any version), the basic setup
for these lines can be similar to the following:
Line 8 - C:\BBS\BULL\BULL#.BBS <- Bulletin w/@codes is created
Line 9 - <- Leave Blank
Line 10 - WC <- Specifies WC @codes
* PCBoard Users
If you are running a PCBoard BBS, then you can setup these lines
similar to the following:
Line 8 - C:\BBS\BULL\BULL#.ANS <- Color Bulletin path and name
Line 9 - C:\BBS\BULL\BULL#.ASC <- Mono Bulletin path and name
Line 10 - PCB <- Specifies PCBoard Color codes
* General
If you are running a BBS that creates ANS/ASC type bulletins then
you can use something like...
Line 8 - C:\BBS\BULL\BULL#.ANS <- Color Bulletin path and name
Line 9 - C:\BBS\BULL\BULL#.ASC <- Mono Bulletin path and name
Line 10 - <- Leave Blank to create ANS/ASC
type bulletins.
Note: If your BBS does not display the color bulletin with the
extension name of .ANS, but will if it's .SCR just change the
extension to .SCR. On the same note, if it doesn't display the
Mono bulletin with the extension name of .ASC, then put the name
of the extension of what it will display.
EXCEPTION: NONE
**** ERROR #53 - File not found
ERROR #64 - Bad file name
ERROR #75 - Path/File access error
ERROR #76 - Path not found
CAUSE: NOT having either the correct path and/or filename for the door
drop file...(ie where the program can find the DOOR.SYS file).
CURE: Make sure that you have the EXACT Path AND Name of the drop file
that your BBS Software requires to run.
EXCEPTION: NONE
**** ERROR #62 - Input past end of file
ERROR #63 - Bad record number
CAUSE: NOT having enough lines in the .CFG file. There's either too
many or not enough lines in the .CFG file.
CURE: Make sure that ALL the lines that the .CFG requires is what it
actually has. Also double check to make sure that one of the
lines was not inadvertently deleted when it was being edited.
EXCEPTION: NONE
_____________________________________________________________________________
If you are operating on 486 computer and getting a "keyboard timeout", you
will need to set the following environment variable in your AUTOEXEC.BAT.
SET NO87=ON
This will inform DoorFrame to use a different timing routine. If you are
operating under DESQview/X, you must flag the MATH COPROCESSOR as being ON.
If the door seems to operate fine on the BBS end but the remote cannot
receive or receives garbled info, check and make sure you are passing the
correct IRQ to the door. Comm 1 and 2 are standard and as such you do
not need to pass the IRQ to them.
If you are operating under DESQview, you will need to load DVANSI in
EACH window.
Unless you are using a Digi-board and need a fossil driver, DO NOT use
the "/FD" switch on the command line. The doors do not need a fossil
driver to operate on serial ports.
-= END =-